You can use Links reports to verify that the links you specify to items in your source documents resolve and that ePublisher processed links in your source documents to the item referenced by the link correctly. Links reports provide notifications on the following items:

  • Baggage files

  • External URLs

  • Unresolved links to items in other documents

  • Unresolved links to missing source document

  • Unresolved links to missing files

  • Unresolved link within source documents document

  • Unsupported baggage files

  • Unsupported external URLs

  • Unsupported group to group links

  • Runtime hash links, in WebWorks Reverb 2.0 output

A runtime hash link, such as #/<source-id>, #context/, #page/, or #search/, resolves in the reader's browser rather than at generation time, so ePublisher cannot verify it while generating output. In releases before 2026.1, the Links report counted every runtime hash link as an unresolved link, even though the published link works. Since 2026.1, WebWorks Reverb 2.0 targets classify these links under the separate Runtime hash link setting instead, which defaults to Ignore, so they no longer appear in the report; a link to an anchor that is genuinely missing is still reported as unresolved. Output formats without a runtime to resolve these links continue to report them as unresolved links. For more information, see Target Settings Reference.

For the definition of a baggage file see Targets.

Configure the notification you want ePublisher to generate for Links report settings before you generate Links reports. For more information about configuring Links report settings, see Configuring Reports. For more information about generating Links reports, see Generating Reports.

Last modified date: 08/17/2026